Vcenter Namespaces NamespaceTemplates UpdateSpec

Vcenter Namespaces NamespaceTemplates UpdateSpec
Vcenter Namespaces NamespaceTemplates UpdateSpec

The Vcenter Namespaces NamespaceTemplates UpdateSpec schema contains the specification required to update a namespace namespace template.

This schema was added in vSphere API 7.0.2.00100.

JSON Example
{
    "resource_spec": {},
    "storage_specs": [
        {
            "policy": "string",
            "limit": 0
        }
    ],
    "networks": [
        "string"
    ],
    "permissions": [
        {
            "subject_type": "string",
            "subject": "string",
            "domain": "string"
        }
    ],
    "vm_service_spec": {
        "content_libraries": [
            "string"
        ],
        "vm_classes": [
            "string"
        ]
    },
    "content_libraries": [
        {
            "content_library": "string",
            "writable": false,
            "allow_import": false,
            "resource_naming_strategy": "string"
        }
    ]
}
object
resource_spec
Optional

Resource quota on the namespace. Refer to Vcenter NamespaceManagement NamespaceResourceOptions Info.create_resource_quota_type and use GET /vcenter/namespace-management/clusters/{cluster}/workload-resource-options for retrieving the type for the value for this field. For an example of this, see Vcenter Namespaces ResourceQuotaOptionsV1.

This property was added in vSphere API 7.0.2.00100.

If missing or null, no resource limits will be set on the namespace.

storage_specs
Optional

Storage that this template defines and will be associated with a namespace after namespace realization.

This property was added in vSphere API 7.0.2.00100.

If missing or null then no update will be made.

array of string
networks
Optional

vSphere Namespaces network objects to be associated with the namespace. The values of this list need to reference names of pre-existing Vcenter NamespaceManagement Networks Info schemas.

This property was added in vSphere API 7.0.2.00100.

The field must be left missing or null if the cluster hosting the namespace uses NSXT_CONTAINER_PLUGIN or NSX_VPC as the network provider, since the network(s) for this namespace will be managed by NSX Container Plugin. If field is missing or null when the cluster hosting the namespace uses VSPHERE_NETWORK as its network provider, the namespace will automatically be associated with the cluster's Supervisor Primary Workload Network. The field currently accepts at most only 1 vSphere Namespaces network object reference.

When clients pass a value of this schema as a parameter, the property must contain identifiers for the resource type: com.vmware.vcenter.namespace_management.Network. When operations return a value of this schema as a response, the property will contain identifiers for the resource type: com.vmware.vcenter.namespace_management.Network.

permissions
Optional

Permissions associated with namespace template.

This property was added in vSphere API 7.0.2.00100.

If missing or null, only users with the Administrator role can use this template; for example, this template is applied to the namespace created by self-service-users with the Administrator role.

vm_service_spec
Optional

VM Service specification to be associated with the namespace template. The virtual machine classes and Content Library associations of the template will be updated according to this {UpdateSpec#vmServiceSpec}.

This property was added in vSphere API 7.0.3.2.

If missing or null, the namespaces created using this template will not have access to any virtual machine classes by default, and to any Content Libraries by default unless Content Libraries are specified in the {UpdateSpec#contentLibraries}.

content_libraries
Optional

Content Library specifications to be associated with the namespace template. Namespaces created using this template will have access to the Content Libraries specified in this {UpdateSpec#contentLibraries} by default.

This property was added in vSphere API 8.0.2.0.

If missing or null, the namespaces created using this template will not have access to any Content Libraries by default unless Content Libraries are specified in the {UpdateSpec#vmServiceSpec}.